Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b648699728c8546ebbb7d6a9f17c937464fcd1ba97455e43df1c9521e9566cd

Tx prefix hash: 9bd2ec0bc90cf6e87c33d6103b7e5912a56eff1d141cab2ca830836d9b9453e8
Tx public key: 54a7d455cb4c0a0f03dcf97ba74724dfa1f61a436d3759753d6b67611044a47f
Timestamp: 1726590074 Timestamp [UCT]: 2024-09-17 16:21:14 Age [y:d:h:m:s]: 00:058:10:35:58
Block: 1112186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41762 RingCT/type: yes/0
Extra: 0154a7d455cb4c0a0f03dcf97ba74724dfa1f61a436d3759753d6b67611044a47f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14a318126f479a96b655349df09b39103f53bc5f972a6401a07837aee5b2e5aa 0.600000000000 1591419 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": 1112196, "vin": [ { "gen": { "height": 1112186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a318126f479a96b655349df09b39103f53bc5f972a6401a07837aee5b2e5aa" } } ], "extra": [ 1, 84, 167, 212, 85, 203, 76, 10, 15, 3, 220, 249, 123, 167, 71, 36, 223, 161, 246, 26, 67, 109, 55, 89, 117, 61, 107, 103, 97, 16, 68, 164, 127, 2, 17, 0, 0, 0, 5, 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