Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdce474d9b2978ca11c3711a6e97b1b5d2cf24e3acf42ce36b5fe16e460aaae1

Tx prefix hash: 38e9827781470a8b4a8f5714da64ca41a7eb91a21e4f45c4f059beec21bc953e
Tx public key: 96bbeaea30381d86161c9e659f7d99f29562eadb51bab25d119fba4c27f318d0
Timestamp: 1646029995 Timestamp [UTC]: 2022-02-28 06:33:15 Age [y:d:h:m:s]: 04:266:21:57:15
Block: 448155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1235009 RingCT/type: yes/0
Extra: 0196bbeaea30381d86161c9e659f7d99f29562eadb51bab25d119fba4c27f318d0021100000004a272b9cb000000000000000000

1 output(s) for total of 0.020094717981 xmr

stealth address amount amount idx tag
00: 4375937e5feaa3a4c69be3f76493298c0526ff38b68c7d5a6ca7cc0ab7d3797f 0.020094717981 862450 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": 448165, "vin": [ { "gen": { "height": 448155 } } ], "vout": [ { "amount": 20094717981, "target": { "key": "4375937e5feaa3a4c69be3f76493298c0526ff38b68c7d5a6ca7cc0ab7d3797f" } } ], "extra": [ 1, 150, 187, 234, 234, 48, 56, 29, 134, 22, 28, 158, 101, 159, 125, 153, 242, 149, 98, 234, 219, 81, 186, 178, 93, 17, 159, 186, 76, 39, 243, 24, 208, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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: