Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ffbe6a759d63a72e436cbb69cbf49d25d934d0ca6b56644e420a9eefb4b4a9e0

Tx prefix hash: f76f605c278217274d2544cac6833572f7a3396c7d6b1a9c69c5f57013fda6d4
Tx public key: bc8780d11f60679db4fbbf41f3e64d74e6eea009bc70e70e863cf53d105d182b
Timestamp: 1734934950 Timestamp [UCT]: 2024-12-23 06:22:30 Age [y:d:h:m:s]: 00:120:02:02:46
Block: 1181285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85586 RingCT/type: yes/0
Extra: 01bc8780d11f60679db4fbbf41f3e64d74e6eea009bc70e70e863cf53d105d182b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f645333e873af42289dd615e14c13344c0395b2dd83d35f241ff9b7413785de 0.600000000000 1667702 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1181295, "vin": [ { "gen": { "height": 1181285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f645333e873af42289dd615e14c13344c0395b2dd83d35f241ff9b7413785de" } } ], "extra": [ 1, 188, 135, 128, 209, 31, 96, 103, 157, 180, 251, 191, 65, 243, 230, 77, 116, 230, 238, 160, 9, 188, 112, 231, 14, 134, 60, 245, 61, 16, 93, 24, 43, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8