Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1552b79a1e3dad0889e618f3fd4842542d1a32433e968005dcc9bc46eafd5c66

Tx prefix hash: 0862bfbdb02aa91c31ed825bb7f485af798b62a558229afbc0811219b16c744b
Tx public key: 9fee11cefbcc83295c79e9344052f819b943ef2a1fa7c9bfa9ed91125504e09b
Timestamp: 1706126073 Timestamp [UTC]: 2024-01-24 19:54:33 Age [y:d:h:m:s]: 02:112:08:49:15
Block: 942509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592364 RingCT/type: yes/0
Extra: 019fee11cefbcc83295c79e9344052f819b943ef2a1fa7c9bfa9ed91125504e09b02110000000352d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: db189c664bc07b26275f53e77036b226eacf3c112395bf195fafc96e32bc522b 0.000600000000 1400681 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": 942519, "vin": [ { "gen": { "height": 942509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db189c664bc07b26275f53e77036b226eacf3c112395bf195fafc96e32bc522b" } } ], "extra": [ 1, 159, 238, 17, 206, 251, 204, 131, 41, 92, 121, 233, 52, 64, 82, 248, 25, 185, 67, 239, 42, 31, 167, 201, 191, 169, 237, 145, 18, 85, 4, 224, 155, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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: