Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd88a6512a1b6dd5823720bbd8a9e3da97c9a178189b3f2f7e16f3f302efc95a

Tx prefix hash: 7d0cc9d19d293fb993d24e215bf06e52729d6cc31161d73bb75e4d4219279940
Tx public key: 57137d969e4b45152f8e41e99f13bcba6dbc20f15cabf8b50f5b17af1c28c00d
Timestamp: 1760846436 Timestamp [UTC]: 2025-10-19 04:00:36 Age [y:d:h:m:s]: 01:026:22:52:46
Block: 1393092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285493 RingCT/type: yes/0
Extra: 0157137d969e4b45152f8e41e99f13bcba6dbc20f15cabf8b50f5b17af1c28c00d0211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 795b8fb6cf0fea5e0477982989cba102fcf067c5ce78a189cf3dbf827b8efef7 0.000600000000 1881349 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": 1393102, "vin": [ { "gen": { "height": 1393092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "795b8fb6cf0fea5e0477982989cba102fcf067c5ce78a189cf3dbf827b8efef7" } } ], "extra": [ 1, 87, 19, 125, 150, 158, 75, 69, 21, 47, 142, 65, 233, 159, 19, 188, 186, 109, 188, 32, 241, 92, 171, 248, 181, 15, 91, 23, 175, 28, 40, 192, 13, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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: