Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820f9769bcfb08f080b96e48331ff5c996b43e7dbe196e3e096af35c05684188

Tx prefix hash: 9f84e803e6fc9ba0f1b8f1990cccde95f40a0d8fc7ba59b8e65cde3f87778fe4
Tx public key: 428c6ba7c40d86b0d7a6ac77f30d6bcf33229f1681208c79813105911ffb6510
Timestamp: 1774975364 Timestamp [UTC]: 2026-03-31 16:42:44 Age [y:d:h:m:s]: 00:232:21:21:35
Block: 1509915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172026 RingCT/type: yes/0
Extra: 01428c6ba7c40d86b0d7a6ac77f30d6bcf33229f1681208c79813105911ffb6510021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7345a813111c53d88b902abc260f7e53f45c4e9ba1081dc7a84d5a5a61f857fa 0.000600000000 1999691 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": 1509925, "vin": [ { "gen": { "height": 1509915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7345a813111c53d88b902abc260f7e53f45c4e9ba1081dc7a84d5a5a61f857fa" } } ], "extra": [ 1, 66, 140, 107, 167, 196, 13, 134, 176, 215, 166, 172, 119, 243, 13, 107, 207, 51, 34, 159, 22, 129, 32, 140, 121, 129, 49, 5, 145, 31, 251, 101, 16, 2, 17, 0, 0, 0, 2, 238, 75, 113, 129, 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: