Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dafc64adfcf3b3ad89b979fe751847ee0fd9c3c76e69c5e05aaa15652f8c4f55

Tx prefix hash: 6137ea61e36848a83baa3ec9e32d695501e7256fb33f9f4d766db1b75761c182
Tx public key: 889bcd36667c60ef469878ce68dd7ec54a415aa89ddc04159c1394df2e96ae77
Timestamp: 1729004463 Timestamp [UTC]: 2024-10-15 15:01:03 Age [y:d:h:m:s]: 02:035:04:48:14
Block: 1132214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549900 RingCT/type: yes/0
Extra: 01889bcd36667c60ef469878ce68dd7ec54a415aa89ddc04159c1394df2e96ae7702110000000591e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81d518bc6f6192884f40882138be9f555f4ad0abcb8b5d49a26214e1e81cbb16 0.000600000000 1615127 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": 1132224, "vin": [ { "gen": { "height": 1132214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d518bc6f6192884f40882138be9f555f4ad0abcb8b5d49a26214e1e81cbb16" } } ], "extra": [ 1, 136, 155, 205, 54, 102, 124, 96, 239, 70, 152, 120, 206, 104, 221, 126, 197, 74, 65, 90, 168, 157, 220, 4, 21, 156, 19, 148, 223, 46, 150, 174, 119, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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: