Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 016d33b8a8b2447cb52a50475714356d1e8033493527fd47bb984aa083431ff1

Tx prefix hash: a06e8e3f4d0a64646f0306cf1dcf274c3b51449504b222a6bb1487a338900c85
Tx public key: be9a346e74e1661ab465fc70df97ac5b24ea7d3eac0ed504071fb1d76c4d4b84
Timestamp: 1704989842 Timestamp [UCT]: 2024-01-11 16:17:22 Age [y:d:h:m:s]: 01:316:16:48:25
Block: 933106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485181 RingCT/type: yes/0
Extra: 01be9a346e74e1661ab465fc70df97ac5b24ea7d3eac0ed504071fb1d76c4d4b840211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f97ace49bef326c2e9db5d6ce3163abae68af7e138f56f5b3fb0f14faf04a30 0.600000000000 1391058 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": 933116, "vin": [ { "gen": { "height": 933106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f97ace49bef326c2e9db5d6ce3163abae68af7e138f56f5b3fb0f14faf04a30" } } ], "extra": [ 1, 190, 154, 52, 110, 116, 225, 102, 26, 180, 101, 252, 112, 223, 151, 172, 91, 36, 234, 125, 62, 172, 14, 213, 4, 7, 31, 177, 215, 108, 77, 75, 132, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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