Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 978791bc4bc90296ffadf21d949417dd9c33f6ee8d43cf9607750e632296950e

Tx prefix hash: 2d844057fd963a93e50eca5eef9788366306a1fe0b19f8a15b2e0af7301dc8ad
Tx public key: 1a874da01956f6ae197a240a5db00f3bb0cab3ae104909052cfee200cf0097d4
Timestamp: 1738852081 Timestamp [UTC]: 2025-02-06 14:28:01 Age [y:d:h:m:s]: 01:198:11:02:11
Block: 1213420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406185 RingCT/type: yes/0
Extra: 011a874da01956f6ae197a240a5db00f3bb0cab3ae104909052cfee200cf0097d402110000000927ff1f91000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de373aa18b2a9ffd8fc759c3e832f33233b68379fdcf55e056bf345eedfb6e8b 0.000600000000 1700199 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": 1213430, "vin": [ { "gen": { "height": 1213420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de373aa18b2a9ffd8fc759c3e832f33233b68379fdcf55e056bf345eedfb6e8b" } } ], "extra": [ 1, 26, 135, 77, 160, 25, 86, 246, 174, 25, 122, 36, 10, 93, 176, 15, 59, 176, 202, 179, 174, 16, 73, 9, 5, 44, 254, 226, 0, 207, 0, 151, 212, 2, 17, 0, 0, 0, 9, 39, 255, 31, 145, 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: