Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beaaa6c1f3e7a0dff9b96f2fb4e6ea8271dffebec640029712090c854bf11134

Tx prefix hash: c23c6398e8473709eef5377e45ea4bcfb5cf057686fa8d6f51482ca0d8c03aa8
Tx public key: a78525c12a04fcc0d5679aca75562307fa4e571e303851e9478f987e5757c184
Timestamp: 1773885572 Timestamp [UTC]: 2026-03-19 01:59:32 Age [y:d:h:m:s]: 00:240:20:31:40
Block: 1500887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177564 RingCT/type: yes/0
Extra: 01a78525c12a04fcc0d5679aca75562307fa4e571e303851e9478f987e5757c184021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5acb9438c214747d1b95ec9626d25b9b5699e374c3817187a396b621dd61e96d 0.000600000000 1990563 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": 1500897, "vin": [ { "gen": { "height": 1500887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5acb9438c214747d1b95ec9626d25b9b5699e374c3817187a396b621dd61e96d" } } ], "extra": [ 1, 167, 133, 37, 193, 42, 4, 252, 192, 213, 103, 154, 202, 117, 86, 35, 7, 250, 78, 87, 30, 48, 56, 81, 233, 71, 143, 152, 126, 87, 87, 193, 132, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: