Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba90a6fdc6f43c4ea33241dbb182b23fdd4f500deeed4517d74de6e2b86e41d9

Tx prefix hash: c2781881107d7c1623330df44f1d80faeb217b359cfff30c5df4da2b140a79b6
Tx public key: 6756c1115d1ce46be50a11f842e71bacef0876548e6df73fb6554c86faa5b018
Timestamp: 1744671431 Timestamp [UTC]: 2025-04-14 22:57:11 Age [y:d:h:m:s]: 01:217:08:06:51
Block: 1261578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419384 RingCT/type: yes/0
Extra: 016756c1115d1ce46be50a11f842e71bacef0876548e6df73fb6554c86faa5b0180211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08906bbbb849aef6001c4d0c8a4077d7276f2ce941fa8e4f499919c5bc454b34 0.000600000000 1748751 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": 1261588, "vin": [ { "gen": { "height": 1261578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08906bbbb849aef6001c4d0c8a4077d7276f2ce941fa8e4f499919c5bc454b34" } } ], "extra": [ 1, 103, 86, 193, 17, 93, 28, 228, 107, 229, 10, 17, 248, 66, 231, 27, 172, 239, 8, 118, 84, 142, 109, 247, 63, 182, 85, 76, 134, 250, 165, 176, 24, 2, 17, 0, 0, 0, 1, 108, 152, 170, 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) | monero version: