Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d864fd013a4ecd76a59eb45c92ff9fc3232bdd7caba235e1f4e4770c854405

Tx prefix hash: 083052a0d032f170f684bdefb4adb1c7d4506841849a248f9a0bad64ad5e2117
Tx public key: 684cc30d58b4d6d9c9b2da58498e88c710de67afae9bcede22a12a944545e47d
Timestamp: 1714997619 Timestamp [UCT]: 2024-05-06 12:13:39 Age [y:d:h:m:s]: 00:235:17:38:54
Block: 1016079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168730 RingCT/type: yes/0
Extra: 01684cc30d58b4d6d9c9b2da58498e88c710de67afae9bcede22a12a944545e47d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f6479f57a542868234fb38c09b5213d8fdd6bfb53291519272c93aaf1ad9bcc 0.600000000000 1479562 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": 1016089, "vin": [ { "gen": { "height": 1016079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f6479f57a542868234fb38c09b5213d8fdd6bfb53291519272c93aaf1ad9bcc" } } ], "extra": [ 1, 104, 76, 195, 13, 88, 180, 214, 217, 201, 178, 218, 88, 73, 142, 136, 199, 16, 222, 103, 175, 174, 155, 206, 222, 34, 161, 42, 148, 69, 69, 228, 125, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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