Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83e2a5e45d1821347b2c8df340dcb89d916eb1e4a17b49e9bf59a8e9bad7a8b7

Tx prefix hash: 0bfc97349a6c9e60ea439b7836759097119e7926e35266301c4353f4c5dfc376
Tx public key: 2ef239aafb5afb8e4f214f4121667eebc669639448305655d71fd1db3d32c557
Timestamp: 1704288154 Timestamp [UTC]: 2024-01-03 13:22:34 Age [y:d:h:m:s]: 02:070:04:22:10
Block: 927305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569792 RingCT/type: yes/0
Extra: 012ef239aafb5afb8e4f214f4121667eebc669639448305655d71fd1db3d32c55702110000000c0011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 446e6d8662c061e8fd88f2d81cb13466fe61f47b6b1fb31eecabdb0f9195cacb 0.000600000000 1385141 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 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": 927315, "vin": [ { "gen": { "height": 927305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446e6d8662c061e8fd88f2d81cb13466fe61f47b6b1fb31eecabdb0f9195cacb" } } ], "extra": [ 1, 46, 242, 57, 170, 251, 90, 251, 142, 79, 33, 79, 65, 33, 102, 126, 235, 198, 105, 99, 148, 72, 48, 86, 85, 215, 31, 209, 219, 61, 50, 197, 87, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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