Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a55061a0ad4bea5241e863bc8e4f237b1562dc1aea0b4f07d62a9bc8753bcb

Tx prefix hash: 8a41a10cf4b95063c045a97140893cdb5a4be606a988f04fc4b06f2327e95bfe
Tx public key: 32cb03fca0defc171cf5956d167828256225fe03b1eb89f3bea3439308735802
Timestamp: 1635375805 Timestamp [UTC]: 2021-10-27 23:03:25 Age [y:d:h:m:s]: 04:201:05:11:49
Block: 361849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173009 RingCT/type: yes/0
Extra: 0132cb03fca0defc171cf5956d167828256225fe03b1eb89f3bea343930873580202110000000406faf294000000000000000000

1 output(s) for total of 0.038821850283 xmr

stealth address amount amount idx tag
00: 4d6e76f42719d27e231040dc1f39380e6ea36ac33b9f081e9c3161303068771b 0.038821850283 736005 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": 361859, "vin": [ { "gen": { "height": 361849 } } ], "vout": [ { "amount": 38821850283, "target": { "key": "4d6e76f42719d27e231040dc1f39380e6ea36ac33b9f081e9c3161303068771b" } } ], "extra": [ 1, 50, 203, 3, 252, 160, 222, 252, 23, 28, 245, 149, 109, 22, 120, 40, 37, 98, 37, 254, 3, 177, 235, 137, 243, 190, 163, 67, 147, 8, 115, 88, 2, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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) | monero version: