Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322bad182ec5910c52854064d5826895eccd0912e5ecbd471b72926c1fce2dc4

Tx prefix hash: 438faf8402e773eaa71307f4a9dccb2be7fe33ac7f1f98911f3a78e5d6917499
Tx public key: 24d40472cccbfbc4a2df923048429089dba28f9f163d074fca93603e399d8cde
Timestamp: 1724649094 Timestamp [UCT]: 2024-08-26 05:11:34 Age [y:d:h:m:s]: 00:080:21:44:51
Block: 1096090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57858 RingCT/type: yes/0
Extra: 0124d40472cccbfbc4a2df923048429089dba28f9f163d074fca93603e399d8cde02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4c70eb637a7bf08f7a08e6d127fa016ad7b3fd2a74e9225bbb97e9c6e8cc42 0.600000000000 1571277 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": 1096100, "vin": [ { "gen": { "height": 1096090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4c70eb637a7bf08f7a08e6d127fa016ad7b3fd2a74e9225bbb97e9c6e8cc42" } } ], "extra": [ 1, 36, 212, 4, 114, 204, 203, 251, 196, 162, 223, 146, 48, 72, 66, 144, 137, 219, 162, 143, 159, 22, 61, 7, 79, 202, 147, 96, 62, 57, 157, 140, 222, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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