Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f701b7dfbb49941cfc3e720b1cb372284c1789c265f5f98d7efaa25c7ce8259

Tx prefix hash: 55fe37a7f07885a19058f3f2d7c59f09ad3db23e91d3037e673797d11fc3d66a
Tx public key: 54fc1a443a54f56bd1265d22614cb0fdaaa9626a248830091c31562c8f453cbc
Timestamp: 1579569933 Timestamp [UTC]: 2020-01-21 01:25:33 Age [y:d:h:m:s]: 06:029:02:54:13
Block: 49675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1429835 RingCT/type: yes/0
Extra: 0154fc1a443a54f56bd1265d22614cb0fdaaa9626a248830091c31562c8f453cbc02110000000149b77a3d000000000000000000

1 output(s) for total of 0.420152485827 xmr

stealth address amount amount idx tag
00: 383d0b3d7e3bbed563d723513e1b95f032a9258b39432f82f6ac1901894fb70c 0.420152485827 92289 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": 49685, "vin": [ { "gen": { "height": 49675 } } ], "vout": [ { "amount": 420152485827, "target": { "key": "383d0b3d7e3bbed563d723513e1b95f032a9258b39432f82f6ac1901894fb70c" } } ], "extra": [ 1, 84, 252, 26, 68, 58, 84, 245, 107, 209, 38, 93, 34, 97, 76, 176, 253, 170, 169, 98, 106, 36, 136, 48, 9, 28, 49, 86, 44, 143, 69, 60, 188, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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