Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: decf43eb1fc0b3ae4fc8ce4a1a8e55bfdfe2a6e192abab42555f0114bd19667a

Tx prefix hash: d19626bfb83720beb9c357a65c56baf1947fbf631ec93b39aeac8796f1a2221a
Tx public key: 6a32675649aaf15426250172592166821fb7e0ac7b0eeb32da110d3f432941f5
Timestamp: 1738528192 Timestamp [UTC]: 2025-02-02 20:29:52 Age [y:d:h:m:s]: 01:100:01:47:06
Block: 1210727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322416 RingCT/type: yes/0
Extra: 016a32675649aaf15426250172592166821fb7e0ac7b0eeb32da110d3f432941f5021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5620e4a13d4dc57c951b6403e92f6cc47f1b6c162ad64f1990bd7509b4cce83c 0.000600000000 1697482 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": 1210737, "vin": [ { "gen": { "height": 1210727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5620e4a13d4dc57c951b6403e92f6cc47f1b6c162ad64f1990bd7509b4cce83c" } } ], "extra": [ 1, 106, 50, 103, 86, 73, 170, 241, 84, 38, 37, 1, 114, 89, 33, 102, 130, 31, 183, 224, 172, 123, 14, 235, 50, 218, 17, 13, 63, 67, 41, 65, 245, 2, 17, 0, 0, 0, 2, 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: