Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec06947bf5dc9510849646c9873f2e2f9b033a2f19f4ff9a6526fd54b90d4ff1

Tx prefix hash: 6cdf9f0007c21447f12cea35a5681421ff4aceefd0b9ba0db6de8174bc172220
Tx public key: 579033daa44b09163dce53e7d406f7abb8531fb7c78581c54a70969eea1da49c
Timestamp: 1724635280 Timestamp [UCT]: 2024-08-26 01:21:20 Age [y:d:h:m:s]: 00:090:06:45:30
Block: 1095972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64583 RingCT/type: yes/0
Extra: 01579033daa44b09163dce53e7d406f7abb8531fb7c78581c54a70969eea1da49c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6cf0f53c372df587fad2d1fd6d7ae76685360ee0d906b546988e64f8e03d9a0 0.600000000000 1571159 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": 1095982, "vin": [ { "gen": { "height": 1095972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6cf0f53c372df587fad2d1fd6d7ae76685360ee0d906b546988e64f8e03d9a0" } } ], "extra": [ 1, 87, 144, 51, 218, 164, 75, 9, 22, 61, 206, 83, 231, 212, 6, 247, 171, 184, 83, 31, 183, 199, 133, 129, 197, 74, 112, 150, 158, 234, 29, 164, 156, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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