Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38d793ef6143492be23ccbe43f979bc978d4a75774f6e61a47f5e1dc0088459

Tx prefix hash: f5f881a1c05645d7759b8f37eb75162472b48d7005cfb97ff5f0d1cb666a9d0e
Tx public key: a7292c8c87360580dd01642727a97f338ea74a77e9c897b68a015ff66407f4cb
Timestamp: 1723867658 Timestamp [UCT]: 2024-08-17 04:07:38 Age [y:d:h:m:s]: 00:262:13:05:56
Block: 1089625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187537 RingCT/type: yes/0
Extra: 01a7292c8c87360580dd01642727a97f338ea74a77e9c897b68a015ff66407f4cb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368c0534daeb4c5cf754d643af83dcbbbfd9c37f631390e1535199f730777bb6 0.600000000000 1564248 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": 1089635, "vin": [ { "gen": { "height": 1089625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368c0534daeb4c5cf754d643af83dcbbbfd9c37f631390e1535199f730777bb6" } } ], "extra": [ 1, 167, 41, 44, 140, 135, 54, 5, 128, 221, 1, 100, 39, 39, 169, 127, 51, 142, 167, 74, 119, 233, 200, 151, 182, 138, 1, 95, 246, 100, 7, 244, 203, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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