Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ca719c7d4c2b678c23654c90648d73ca5e620b6a529fcf4eccc09afb28469d1

Tx prefix hash: 743846a932e89841c4628f3ad1ae86f0140ca0c3b0a6d6e8ea467d00f6011428
Tx public key: 7f249b7253a19e3150360c207ffb1c49b81871a5882967ca8a2372d5fc1522a2
Timestamp: 1748807973 Timestamp [UTC]: 2025-06-01 19:59:33 Age [y:d:h:m:s]: 01:169:18:45:12
Block: 1295836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385356 RingCT/type: yes/0
Extra: 017f249b7253a19e3150360c207ffb1c49b81871a5882967ca8a2372d5fc1522a202110000000243846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7abdf51dd1e8c66a1a2df5c9f725191fd1c8acfb1095787716e8e65a3b287fc7 0.000600000000 1783343 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": 1295846, "vin": [ { "gen": { "height": 1295836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7abdf51dd1e8c66a1a2df5c9f725191fd1c8acfb1095787716e8e65a3b287fc7" } } ], "extra": [ 1, 127, 36, 155, 114, 83, 161, 158, 49, 80, 54, 12, 32, 127, 251, 28, 73, 184, 24, 113, 165, 136, 41, 103, 202, 138, 35, 114, 213, 252, 21, 34, 162, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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: