Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3cfade2de2c7c05713915adef870f50e83dd22c23318eeb0b5782efd98bc23

Tx prefix hash: 7e995b442df2ba2e2b7ce0e4f80ce5e4aa657ee0ed371697bb7c2e78774ac917
Tx public key: bf1e16fd85a2ed4dac5942632cd1e127f4b9151c8f93cbb70d51135736beb6ae
Timestamp: 1747000413 Timestamp [UCT]: 2025-05-11 21:53:33 Age [y:d:h:m:s]: 00:237:18:08:11
Block: 1280869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167714 RingCT/type: yes/0
Extra: 01bf1e16fd85a2ed4dac5942632cd1e127f4b9151c8f93cbb70d51135736beb6ae0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3ef392c48332cd514fff6fd4bf3ab97bbbcff2af2d5332f47b48a1ca1d8079 0.600000000000 1768262 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": 1280879, "vin": [ { "gen": { "height": 1280869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3ef392c48332cd514fff6fd4bf3ab97bbbcff2af2d5332f47b48a1ca1d8079" } } ], "extra": [ 1, 191, 30, 22, 253, 133, 162, 237, 77, 172, 89, 66, 99, 44, 209, 225, 39, 244, 185, 21, 28, 143, 147, 203, 183, 13, 81, 19, 87, 54, 190, 182, 174, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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