Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a7c5088dfc096355fc0efb5fea123de6828dce3cc87457d4fe35dcc87bb11d1

Tx prefix hash: 09d679a02e76196288181e3671da7c1d188b9c79d286aa40cc70b6f48accbcff
Tx public key: e3d3cb6933e89ca000172680fe4c8dba28fd5d554a51d6a600e32b530e7b2b2b
Timestamp: 1703847470 Timestamp [UCT]: 2023-12-29 10:57:50 Age [y:d:h:m:s]: 01:317:19:33:19
Block: 923639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485975 RingCT/type: yes/0
Extra: 01e3d3cb6933e89ca000172680fe4c8dba28fd5d554a51d6a600e32b530e7b2b2b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd9778de7199f209b72bff6271880e1c8f5f2d16aa46275e7327d608271942e 0.600000000000 1381373 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": 923649, "vin": [ { "gen": { "height": 923639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd9778de7199f209b72bff6271880e1c8f5f2d16aa46275e7327d608271942e" } } ], "extra": [ 1, 227, 211, 203, 105, 51, 232, 156, 160, 0, 23, 38, 128, 254, 76, 141, 186, 40, 253, 93, 85, 74, 81, 214, 166, 0, 227, 43, 83, 14, 123, 43, 43, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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