Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a4f967b2fb85e27458dc3610f0be967f4a1fddc8b941e0fae6e4f04cba66853

Tx prefix hash: d2ffb1ea5c65ac592660c27d29ab409d66536e9921027a691d6ad4f43f7b45b1
Tx public key: 5d45f674db2124d9d87ae8ff6821ec7a94ea043fa73943c33d19b44a35cfa6e8
Timestamp: 1712416646 Timestamp [UCT]: 2024-04-06 15:17:26 Age [y:d:h:m:s]: 00:364:11:32:04
Block: 994663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260598 RingCT/type: yes/0
Extra: 015d45f674db2124d9d87ae8ff6821ec7a94ea043fa73943c33d19b44a35cfa6e802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b74f125045b6ff9fce9f147138c087d7c8c172b3d4076da69b40cd3c8792c7d5 0.600000000000 1455067 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": 994673, "vin": [ { "gen": { "height": 994663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b74f125045b6ff9fce9f147138c087d7c8c172b3d4076da69b40cd3c8792c7d5" } } ], "extra": [ 1, 93, 69, 246, 116, 219, 33, 36, 217, 216, 122, 232, 255, 104, 33, 236, 122, 148, 234, 4, 63, 167, 57, 67, 195, 61, 25, 180, 74, 53, 207, 166, 232, 2, 17, 0, 0, 0, 3, 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