Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064a9174cfb95e6bb36d05ffc55710d8b2ef0a1678188403061afd371db7a0f5

Tx prefix hash: f73dd53a63be65e8447dbc85a00423681fa24f92565e059d42ee65d9f5aa3e2b
Tx public key: 5fc34c899ade2dee85e9030f998f7e20b0e8a1233df017ccbfa9a1321161e839
Timestamp: 1706540032 Timestamp [UCT]: 2024-01-29 14:53:52 Age [y:d:h:m:s]: 00:300:08:03:32
Block: 945940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215059 RingCT/type: yes/0
Extra: 015fc34c899ade2dee85e9030f998f7e20b0e8a1233df017ccbfa9a1321161e83902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04eb314d20c2ad10e4c850bd0e0e95b16dc00fe803900ad3cc51c00bd5cadbb3 0.600000000000 1404270 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": 945950, "vin": [ { "gen": { "height": 945940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04eb314d20c2ad10e4c850bd0e0e95b16dc00fe803900ad3cc51c00bd5cadbb3" } } ], "extra": [ 1, 95, 195, 76, 137, 154, 222, 45, 238, 133, 233, 3, 15, 153, 143, 126, 32, 176, 232, 161, 35, 61, 240, 23, 204, 191, 169, 161, 50, 17, 97, 232, 57, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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