Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc82d06cfb58fd87d1ad4659de6b99241accd1dce157329303e7845f15c2f330

Tx prefix hash: d6c6932ec9f81847316d6fa95fe8308a0e5574a05e3e7f0e79db4223bdac4553
Tx public key: 43dcfc87cdd028c1c9b83408b37bfe02c6830b2ca0f2e8875ef26601bb9ea5e4
Timestamp: 1741264305 Timestamp [UTC]: 2025-03-06 12:31:45 Age [y:d:h:m:s]: 01:260:01:23:12
Block: 1233389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450062 RingCT/type: yes/0
Extra: 0143dcfc87cdd028c1c9b83408b37bfe02c6830b2ca0f2e8875ef26601bb9ea5e402110000000d007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 45baaa1667b56b9bb41ddb9d6262df3a2bcbe1fb3847cccb19a31989198ee10d 0.000600000000 1720310 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": 1233399, "vin": [ { "gen": { "height": 1233389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45baaa1667b56b9bb41ddb9d6262df3a2bcbe1fb3847cccb19a31989198ee10d" } } ], "extra": [ 1, 67, 220, 252, 135, 205, 208, 40, 193, 201, 184, 52, 8, 179, 123, 254, 2, 198, 131, 11, 44, 160, 242, 232, 135, 94, 242, 102, 1, 187, 158, 165, 228, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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: