Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c7fab25788c4f287671b5aa5f444db35ffd4fbe207e6079c18ea3361d015320

Tx prefix hash: 42f9c6b17362324481257cd1da8268fc049587f0485a34a93d4d847ad048d5bc
Tx public key: 9fe58a9bb6804a402dc0a7aced9eb5846d372ff033761c57b04b7284e0d9b2c8
Timestamp: 1737485107 Timestamp [UCT]: 2025-01-21 18:45:07 Age [y:d:h:m:s]: 00:333:13:20:51
Block: 1202314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235997 RingCT/type: yes/0
Extra: 019fe58a9bb6804a402dc0a7aced9eb5846d372ff033761c57b04b7284e0d9b2c8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b76aeb5b6abb7e5f15788ce87a5e92d28f1b71cc16436aa34fac686e4afa252d 0.600000000000 1688977 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": 1202324, "vin": [ { "gen": { "height": 1202314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b76aeb5b6abb7e5f15788ce87a5e92d28f1b71cc16436aa34fac686e4afa252d" } } ], "extra": [ 1, 159, 229, 138, 155, 182, 128, 74, 64, 45, 192, 167, 172, 237, 158, 181, 132, 109, 55, 47, 240, 51, 118, 28, 87, 176, 75, 114, 132, 224, 217, 178, 200, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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