Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29bb0653c4f5277175fce3514d73dc03dcb1d5791107e048c358d5ab43a3e470

Tx prefix hash: f471867cff1226c9524a07491b72b0c837d85eac51ce22060313c37a24e309e5
Tx public key: a0c4e304b849d2fdf5d335a5a419cccbf39f1f397c3b7ae9493c641e314a4119
Timestamp: 1736175877 Timestamp [UCT]: 2025-01-06 15:04:37 Age [y:d:h:m:s]: 00:087:11:14:32
Block: 1191542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62268 RingCT/type: yes/0
Extra: 01a0c4e304b849d2fdf5d335a5a419cccbf39f1f397c3b7ae9493c641e314a411902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ec87bdd6d01545339d3c171f0219b34af7eb4c79dca5a1fce31cfe44b2eaaeb 0.600000000000 1678081 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": 1191552, "vin": [ { "gen": { "height": 1191542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ec87bdd6d01545339d3c171f0219b34af7eb4c79dca5a1fce31cfe44b2eaaeb" } } ], "extra": [ 1, 160, 196, 227, 4, 184, 73, 210, 253, 245, 211, 53, 165, 164, 25, 204, 203, 243, 159, 31, 57, 124, 59, 122, 233, 73, 60, 100, 30, 49, 74, 65, 25, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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