Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7357d86f8935ee6afc6bb3bbb58863c1251a1e8461fec2b234d80e849d16e31

Tx prefix hash: c2d57c687e2716ab3a6bb2b90d962ccee24fd3ccec91ee094366cfd0b1bc00da
Tx public key: b088eae9e63eb152625f57b39a2015f7142fd57e1e54f38df782ad291316de76
Timestamp: 1714126651 Timestamp [UCT]: 2024-04-26 10:17:31 Age [y:d:h:m:s]: 00:329:09:51:26
Block: 1008866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235476 RingCT/type: yes/0
Extra: 01b088eae9e63eb152625f57b39a2015f7142fd57e1e54f38df782ad291316de760211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbde83307b2e447a5ff0b847ea4b2c1dc5351743446fcd729e90e728f50fe836 0.600000000000 1470352 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": 1008876, "vin": [ { "gen": { "height": 1008866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbde83307b2e447a5ff0b847ea4b2c1dc5351743446fcd729e90e728f50fe836" } } ], "extra": [ 1, 176, 136, 234, 233, 230, 62, 177, 82, 98, 95, 87, 179, 154, 32, 21, 247, 20, 47, 213, 126, 30, 84, 243, 141, 247, 130, 173, 41, 19, 22, 222, 118, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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