Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aef81a85b6801dc567537fa6e40b13d57abcdda4af4f7e6fa66a09cf0f7a1388

Tx prefix hash: 8babbbaa20360eb6b86eaf094150f5561740a4c3734bd3ed58d2495239750266
Tx public key: 6f07e04d1967784c05e1e3a64cda29156398a1a2a410f3b739adb45fcf865a8e
Timestamp: 1717177394 Timestamp [UCT]: 2024-05-31 17:43:14 Age [y:d:h:m:s]: 00:308:19:38:46
Block: 1034157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220706 RingCT/type: yes/0
Extra: 016f07e04d1967784c05e1e3a64cda29156398a1a2a410f3b739adb45fcf865a8e021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8587e64d86775c3da8f005f6a33c7f33b4520b6d82531b136d74a3056d2e6392 0.600000000000 1502640 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": 1034167, "vin": [ { "gen": { "height": 1034157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8587e64d86775c3da8f005f6a33c7f33b4520b6d82531b136d74a3056d2e6392" } } ], "extra": [ 1, 111, 7, 224, 77, 25, 103, 120, 76, 5, 225, 227, 166, 76, 218, 41, 21, 99, 152, 161, 162, 164, 16, 243, 183, 57, 173, 180, 95, 207, 134, 90, 142, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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