Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 674247fb27d707eefe85aef335dc3bd2dda6a8ef912df457ee710e02807ffe73

Tx prefix hash: efefe9adb8800f8024c54b05e98cf34c2b0615efce9770cbd0d2642147e99274
Tx public key: b1d937f5c4e2e038280ace9a645bacbc5520c20ef84023ad4a008a8d8f978d2e
Timestamp: 1771420702 Timestamp [UTC]: 2026-02-18 13:18:22 Age [y:d:h:m:s]: 00:272:10:19:34
Block: 1480506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200220 RingCT/type: yes/0
Extra: 01b1d937f5c4e2e038280ace9a645bacbc5520c20ef84023ad4a008a8d8f978d2e021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 479e8b9221484f6f252abc6120095a1fea3c6cc61ea6b57a38277e9afba6bb63 0.000600000000 1969876 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": 1480516, "vin": [ { "gen": { "height": 1480506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "479e8b9221484f6f252abc6120095a1fea3c6cc61ea6b57a38277e9afba6bb63" } } ], "extra": [ 1, 177, 217, 55, 245, 196, 226, 224, 56, 40, 10, 206, 154, 100, 91, 172, 188, 85, 32, 194, 14, 248, 64, 35, 173, 74, 0, 138, 141, 143, 151, 141, 46, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: