Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2887b952fcd7a343a143d740bf5f8b9ae0d791b843bad7f7df4d62da85a973b6

Tx prefix hash: 6974e85f8c40af54c9602a40d76660d61a378eaa3ac9634527969b3f1be1bb43
Tx public key: 6ee34e94dac8c60dfc0f19e44f00c48de9e25e63217b952d414558c6e982f318
Timestamp: 1747714523 Timestamp [UTC]: 2025-05-20 04:15:23 Age [y:d:h:m:s]: 01:185:22:21:44
Block: 1286787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396707 RingCT/type: yes/0
Extra: 016ee34e94dac8c60dfc0f19e44f00c48de9e25e63217b952d414558c6e982f3180211000000049f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 529b0cb94aaa9f483d0536b1a654bdd7ed071a8b8570b30ba7252c06a42a4d9d 0.000600000000 1774254 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": 1286797, "vin": [ { "gen": { "height": 1286787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "529b0cb94aaa9f483d0536b1a654bdd7ed071a8b8570b30ba7252c06a42a4d9d" } } ], "extra": [ 1, 110, 227, 78, 148, 218, 200, 198, 13, 252, 15, 25, 228, 79, 0, 196, 141, 233, 226, 94, 99, 33, 123, 149, 45, 65, 69, 88, 198, 233, 130, 243, 24, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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: