Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7c3f82726cceaa3064233d139e5f45e25d001fd4b26c6cbd5e2e5812c14f52

Tx prefix hash: 2510add41b1fb618f2536c5f816fc49cc9b495da2fac851e76734e53976ecbe3
Tx public key: db404294b71aa74124fa2f2d4d32fc37b030bff4998fccdd14a032bb9de17639
Timestamp: 1725774931 Timestamp [UCT]: 2024-09-08 05:55:31 Age [y:d:h:m:s]: 00:257:11:42:30
Block: 1105434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183899 RingCT/type: yes/0
Extra: 01db404294b71aa74124fa2f2d4d32fc37b030bff4998fccdd14a032bb9de17639021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a38e978a69d39012d3ea8febea7e4b70e22a5828289276f47a9ab131b5a98e3f 0.600000000000 1582777 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": 1105444, "vin": [ { "gen": { "height": 1105434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a38e978a69d39012d3ea8febea7e4b70e22a5828289276f47a9ab131b5a98e3f" } } ], "extra": [ 1, 219, 64, 66, 148, 183, 26, 167, 65, 36, 250, 47, 45, 77, 50, 252, 55, 176, 48, 191, 244, 153, 143, 204, 221, 20, 160, 50, 187, 157, 225, 118, 57, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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