Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcb4cfaa0072edecd6f6af88d003ff1ff0376dae0bac48ce687b695bc6197efc

Tx prefix hash: cd3b0085a7dae471b8fc29aab8ef4f3628850d729dc547d254e546f4a3ad91c8
Tx public key: 44e4d4a05f32dd86e92caafe2e9b84f6ca3f1a7ede8864eabb0da9cc804fe9ef
Timestamp: 1718072121 Timestamp [UCT]: 2024-06-11 02:15:21 Age [y:d:h:m:s]: 00:170:10:10:43
Block: 1041582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121972 RingCT/type: yes/0
Extra: 0144e4d4a05f32dd86e92caafe2e9b84f6ca3f1a7ede8864eabb0da9cc804fe9ef0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527078cad0ab0a98a6f800ddc427264032b48219a4cb01bc20917274c7dc63b5 0.600000000000 1510291 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": 1041592, "vin": [ { "gen": { "height": 1041582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527078cad0ab0a98a6f800ddc427264032b48219a4cb01bc20917274c7dc63b5" } } ], "extra": [ 1, 68, 228, 212, 160, 95, 50, 221, 134, 233, 44, 170, 254, 46, 155, 132, 246, 202, 63, 26, 126, 222, 136, 100, 234, 187, 13, 169, 204, 128, 79, 233, 239, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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