Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d5558032c5d552b4875f737f5d7f37b7762ba996007936f67d69d7579d6735

Tx prefix hash: f432a36f8184768f7e20bb9f8e94216b3dfdb070d10d1eb242d229d0a8f8791b
Tx public key: 07c48c8df2a6580dd76dd2b58d7bc526aae6508cfc91a0cc0fdadfb543939048
Timestamp: 1725988634 Timestamp [UCT]: 2024-09-10 17:17:14 Age [y:d:h:m:s]: 00:074:20:13:21
Block: 1107206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53507 RingCT/type: yes/0
Extra: 0107c48c8df2a6580dd76dd2b58d7bc526aae6508cfc91a0cc0fdadfb54393904802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43614a7698614e2c23faea047c810517836f49efd032717510320f3c965586e0 0.600000000000 1584813 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": 1107216, "vin": [ { "gen": { "height": 1107206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43614a7698614e2c23faea047c810517836f49efd032717510320f3c965586e0" } } ], "extra": [ 1, 7, 196, 140, 141, 242, 166, 88, 13, 215, 109, 210, 181, 141, 123, 197, 38, 170, 230, 80, 140, 252, 145, 160, 204, 15, 218, 223, 181, 67, 147, 144, 72, 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