Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0400a873b10dc4ef5e424a95c6104400c64a35ef8c0eb367fbade98b6bfdab3

Tx prefix hash: e9d69d6b0991bbd4167da7c6bb2683308aaa41df359145c662a740254dcfab87
Tx public key: 8633f6edc52a45d99418abd0eaac8a25656ba9c1eec68ee9b113d1f11aa0a999
Timestamp: 1734386061 Timestamp [UCT]: 2024-12-16 21:54:21 Age [y:d:h:m:s]: 00:024:20:31:09
Block: 1176732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17754 RingCT/type: yes/0
Extra: 018633f6edc52a45d99418abd0eaac8a25656ba9c1eec68ee9b113d1f11aa0a9990211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385b9a13629e2fe1b304aa02be5d532edae5851b58ec7e3208573dbafd43b686 0.600000000000 1663091 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": 1176742, "vin": [ { "gen": { "height": 1176732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385b9a13629e2fe1b304aa02be5d532edae5851b58ec7e3208573dbafd43b686" } } ], "extra": [ 1, 134, 51, 246, 237, 197, 42, 69, 217, 148, 24, 171, 208, 234, 172, 138, 37, 101, 107, 169, 193, 238, 198, 142, 233, 177, 19, 209, 241, 26, 160, 169, 153, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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