Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fbb2813c4331cd031fd2ca0f1f7c087f67c5cc517ba47739e0399ebd2bd2e73

Tx prefix hash: c46023c4ae44ce795f1c871cd6a80cb003725aed4511214f2f326be5ee982406
Tx public key: 0ed255693a895b2b25376d1340e45497477c6aaba8040b33b4809632123a3187
Timestamp: 1579875963 Timestamp [UTC]: 2020-01-24 14:26:03 Age [y:d:h:m:s]: 06:027:07:17:01
Block: 51892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1428868 RingCT/type: yes/0
Extra: 010ed255693a895b2b25376d1340e45497477c6aaba8040b33b4809632123a318702110000000f8a2ee0d9000000000000000000

1 output(s) for total of 0.413105610051 xmr

stealth address amount amount idx tag
00: ace91ebb25db0e19f67539fe84adce975a83dbc332ded9a619b66a28838f37fa 0.413105610051 96200 of 0 -

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 dinastycoin-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": 51902, "vin": [ { "gen": { "height": 51892 } } ], "vout": [ { "amount": 413105610051, "target": { "key": "ace91ebb25db0e19f67539fe84adce975a83dbc332ded9a619b66a28838f37fa" } } ], "extra": [ 1, 14, 210, 85, 105, 58, 137, 91, 43, 37, 55, 109, 19, 64, 228, 84, 151, 71, 124, 106, 171, 168, 4, 11, 51, 180, 128, 150, 50, 18, 58, 49, 135, 2, 17, 0, 0, 0, 15, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369