Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d5c5b00b6340eef9407f394321aa20da6046ea006ca99ed54f6d97e9cb8fb7

Tx prefix hash: e5f229d2c30c9a5f10885b587dce7a7a0da9099a56f214bc7e7c03e804f6a1a2
Tx public key: add174162d16792981807c331554d39e3d5f82225a1f9c4fcbf46366affcf6d3
Timestamp: 1713588843 Timestamp [UCT]: 2024-04-20 04:54:03 Age [y:d:h:m:s]: 00:252:12:09:31
Block: 1004380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180763 RingCT/type: yes/0
Extra: 01add174162d16792981807c331554d39e3d5f82225a1f9c4fcbf46366affcf6d30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58e5d3dfa3ada079598bd67fd847c8b2f26577b02491a46d44a02240bac7a63a 0.600000000000 1464948 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": 1004390, "vin": [ { "gen": { "height": 1004380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58e5d3dfa3ada079598bd67fd847c8b2f26577b02491a46d44a02240bac7a63a" } } ], "extra": [ 1, 173, 209, 116, 22, 45, 22, 121, 41, 129, 128, 124, 51, 21, 84, 211, 158, 61, 95, 130, 34, 90, 31, 156, 79, 203, 244, 99, 102, 175, 252, 246, 211, 2, 17, 0, 0, 0, 4, 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