Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9779ce0fc85f25f010e0ac50ecad0dc9d1303ab62e26d0233948de1273e32ed4

Tx prefix hash: 28d62eb8f6db261d1f2245bf674127dc892e821b23786c99ed584dab5e8c852f
Tx public key: 44031191119b7257b7316a8c1c9408db2221754a12cbe2ebb60b1c8ebad1e3b3
Timestamp: 1727087860 Timestamp [UCT]: 2024-09-23 10:37:40 Age [y:d:h:m:s]: 00:061:21:13:39
Block: 1116315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44234 RingCT/type: yes/0
Extra: 0144031191119b7257b7316a8c1c9408db2221754a12cbe2ebb60b1c8ebad1e3b302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db6d6c47b728b1b37e64d53a010ee36b49740d8cade741efa3cb83ef4df2187c 0.600000000000 1596754 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": 1116325, "vin": [ { "gen": { "height": 1116315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db6d6c47b728b1b37e64d53a010ee36b49740d8cade741efa3cb83ef4df2187c" } } ], "extra": [ 1, 68, 3, 17, 145, 17, 155, 114, 87, 183, 49, 106, 140, 28, 148, 8, 219, 34, 33, 117, 74, 18, 203, 226, 235, 182, 11, 28, 142, 186, 209, 227, 179, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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