Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47bbd8e787159c1fe075498f3f032f2c6f34193d0bf3dc5f2e6ca952d532ccda

Tx prefix hash: 4e69cd450408d8870a2953e8dda4cb6e2908acd761b9ad56739f9e10fc1cda18
Tx public key: 92e8f5d6c3118ebf82887b5e7e5e4cbb2d870e371a2c0749600769624455651e
Timestamp: 1656871602 Timestamp [UTC]: 2022-07-03 18:06:42 Age [y:d:h:m:s]: 03:237:10:59:36
Block: 535907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 949400 RingCT/type: yes/0
Extra: 0192e8f5d6c3118ebf82887b5e7e5e4cbb2d870e371a2c0749600769624455651e0211000000034da16a3a000000000000000000

1 output(s) for total of 0.010289388276 xmr

stealth address amount amount idx tag
00: 6fbfd4fc15e76b155562c8bbf005375f6738d15e35f7f3b18015e5bbe6b2a3f1 0.010289388276 965578 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": 535917, "vin": [ { "gen": { "height": 535907 } } ], "vout": [ { "amount": 10289388276, "target": { "key": "6fbfd4fc15e76b155562c8bbf005375f6738d15e35f7f3b18015e5bbe6b2a3f1" } } ], "extra": [ 1, 146, 232, 245, 214, 195, 17, 142, 191, 130, 136, 123, 94, 126, 94, 76, 187, 45, 135, 14, 55, 26, 44, 7, 73, 96, 7, 105, 98, 68, 85, 101, 30, 2, 17, 0, 0, 0, 3, 77, 161, 106, 58, 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