Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0986fa5320d2b7d4f1c91e1cf5bf245318686327d24391e7bef05ce3b4e1d72

Tx prefix hash: 281ae13a345c042cb3c116302b9f21e4573daf18bad86702e805d899e59cd8e5
Tx public key: 3c9d80aac3d04899a99574a35b8344f55ee18aecb02da900ea915c1b3c015028
Timestamp: 1702459831 Timestamp [UCT]: 2023-12-13 09:30:31 Age [y:d:h:m:s]: 00:337:00:13:35
Block: 912157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241287 RingCT/type: yes/0
Extra: 013c9d80aac3d04899a99574a35b8344f55ee18aecb02da900ea915c1b3c01502802110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19a7703a4cf786cb8038969271970def86f915d4dc610b249c55c38854d618b0 0.600000000000 1369377 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": 912167, "vin": [ { "gen": { "height": 912157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19a7703a4cf786cb8038969271970def86f915d4dc610b249c55c38854d618b0" } } ], "extra": [ 1, 60, 157, 128, 170, 195, 208, 72, 153, 169, 149, 116, 163, 91, 131, 68, 245, 94, 225, 138, 236, 176, 45, 169, 0, 234, 145, 92, 27, 60, 1, 80, 40, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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