Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898c034fff801f4f470483ecd3c283255712e23fb7b729b8c515579854009a70

Tx prefix hash: ff3a61a992721b0df72b81c33d12ca5324435e1163374531ba3cbb5271c34067
Tx public key: b47535e4916f705e7a39dfabe3ad462e06d77e8ff81fa7aa2339b8d21a1c3a45
Timestamp: 1718652386 Timestamp [UCT]: 2024-06-17 19:26:26 Age [y:d:h:m:s]: 00:305:00:02:11
Block: 1046383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217972 RingCT/type: yes/0
Extra: 01b47535e4916f705e7a39dfabe3ad462e06d77e8ff81fa7aa2339b8d21a1c3a450211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368b4ee0ae92bcbdefb47d65ee2f5c557406059b6d6fa95dcf9a1523bd440861 0.600000000000 1516194 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": 1046393, "vin": [ { "gen": { "height": 1046383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368b4ee0ae92bcbdefb47d65ee2f5c557406059b6d6fa95dcf9a1523bd440861" } } ], "extra": [ 1, 180, 117, 53, 228, 145, 111, 112, 94, 122, 57, 223, 171, 227, 173, 70, 46, 6, 215, 126, 143, 248, 31, 167, 170, 35, 57, 184, 210, 26, 28, 58, 69, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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