Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aba8ce9001e3c62571e9ecff1a45e2b23aa1c9d651f22eb3486f86085f1cf05

Tx prefix hash: 847a1f7f4c6d05fbc52f4eafdbf412954386cb1f321c28a8b26d3ee2e600b9d1
Tx public key: 0718a19b5149fe3de53ca68eb2467c147ff1b8fc2895118217fdabc00682de0c
Timestamp: 1694244162 Timestamp [UCT]: 2023-09-09 07:22:42 Age [y:d:h:m:s]: 01:281:22:29:28
Block: 844209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462543 RingCT/type: yes/0
Extra: 010718a19b5149fe3de53ca68eb2467c147ff1b8fc2895118217fdabc00682de0c02110000000f4b8f5122000000000000000000

1 output(s) for total of 0.979005655000 dcy

stealth address amount amount idx
00: 9b7746f3a7a29c8e4186b8d14d272344187cf09d044ddd58a7ace3385f34cae6 0.979005655000 1297505 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": 844219, "vin": [ { "gen": { "height": 844209 } } ], "vout": [ { "amount": 979005655, "target": { "key": "9b7746f3a7a29c8e4186b8d14d272344187cf09d044ddd58a7ace3385f34cae6" } } ], "extra": [ 1, 7, 24, 161, 155, 81, 73, 254, 61, 229, 60, 166, 142, 178, 70, 124, 20, 127, 241, 184, 252, 40, 149, 17, 130, 23, 253, 171, 192, 6, 130, 222, 12, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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