Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37d8fd6d8f08f198fc8254464ebc7ddacb5c498d567dbca44e8476c1f926613

Tx prefix hash: e1c314a8aeab636984e19c39e5b13d3229f5a0b6b797aa440c1691872fc002cf
Tx public key: 1d480fb26ca20a80b38e71a270ff7cbd03bd5dee92b3f4516ffc62fe8b58b552
Timestamp: 1722306249 Timestamp [UCT]: 2024-07-30 02:24:09 Age [y:d:h:m:s]: 00:249:19:32:09
Block: 1076672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178444 RingCT/type: yes/0
Extra: 011d480fb26ca20a80b38e71a270ff7cbd03bd5dee92b3f4516ffc62fe8b58b55202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9ca728f8752fadace4e53c5c0c7e1e1966233b1343ae11cfde55c674d042b6 0.600000000000 1549213 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": 1076682, "vin": [ { "gen": { "height": 1076672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9ca728f8752fadace4e53c5c0c7e1e1966233b1343ae11cfde55c674d042b6" } } ], "extra": [ 1, 29, 72, 15, 178, 108, 162, 10, 128, 179, 142, 113, 162, 112, 255, 124, 189, 3, 189, 93, 238, 146, 179, 244, 81, 111, 252, 98, 254, 139, 88, 181, 82, 2, 17, 0, 0, 0, 1, 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