Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec24124bf6ab2fee2b1c169f816a18e25ecde7dc9fb46d4ba9d4c35de6d568ed

Tx prefix hash: 8104abd4125afac7d3d0a8c4232af83aea2a010ac37aea8db843361aaa7b5afe
Tx public key: 392a441d325c7e53ab79a39f7da9b5b4016613966e9d85b404dcf3120f2c4d29
Timestamp: 1581255901 Timestamp [UCT]: 2020-02-09 13:45:01 Age [y:d:h:m:s]: 05:270:01:10:30
Block: 61434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343421 RingCT/type: yes/0
Extra: 01392a441d325c7e53ab79a39f7da9b5b4016613966e9d85b404dcf3120f2c4d2902110000000a4ac5aa02000000000000000000

1 output(s) for total of 384.100145574000 dcy

stealth address amount amount idx
00: d3e9d9c5f1b1fbb0e9686727854abc3a08b7ac651b893d489b6032ce3d316842 384.100145574000 113218 of 0

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": 61444, "vin": [ { "gen": { "height": 61434 } } ], "vout": [ { "amount": 384100145574, "target": { "key": "d3e9d9c5f1b1fbb0e9686727854abc3a08b7ac651b893d489b6032ce3d316842" } } ], "extra": [ 1, 57, 42, 68, 29, 50, 92, 126, 83, 171, 121, 163, 159, 125, 169, 181, 180, 1, 102, 19, 150, 110, 157, 133, 180, 4, 220, 243, 18, 15, 44, 77, 41, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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