Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1633504fa52b70fcccca24f3e371a9bc6faaeeae1637f8d834ad09ce4b7ccd84

Tx prefix hash: c9bfc8a44fd6971d6fc811c37b9a2427452ba6b09c5aac7b2b603d7d9bea5463
Tx public key: d4a00d708d5c56a736c751410f055dcf810ec004926d07c595dfe59ad569a99e
Timestamp: 1720242925 Timestamp [UCT]: 2024-07-06 05:15:25 Age [y:d:h:m:s]: 00:270:12:43:50
Block: 1059571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193286 RingCT/type: yes/0
Extra: 01d4a00d708d5c56a736c751410f055dcf810ec004926d07c595dfe59ad569a99e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f3d90eb40b9e10a34fcb91137ff7099204c706b630c93e775c62311f8b1698d 0.600000000000 1530040 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": 1059581, "vin": [ { "gen": { "height": 1059571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f3d90eb40b9e10a34fcb91137ff7099204c706b630c93e775c62311f8b1698d" } } ], "extra": [ 1, 212, 160, 13, 112, 141, 92, 86, 167, 54, 199, 81, 65, 15, 5, 93, 207, 129, 14, 192, 4, 146, 109, 7, 197, 149, 223, 229, 154, 213, 105, 169, 158, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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