Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7d3bf3746bb1ca47661c1f7c63a5683be1c60e12fd3ae6dc4da01abecb4ff30

Tx prefix hash: 1b15728347673e3ff8298034eddc2cc4bd4fdd03e441d23a2170433a63f050bb
Tx public key: fc8c7b56f7f9794ffc92cc3798f6e8482d1836594aca22847115d5c00d14e14d
Timestamp: 1773418807 Timestamp [UTC]: 2026-03-13 16:20:07 Age [y:d:h:m:s]: 00:243:18:06:34
Block: 1497051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179515 RingCT/type: yes/0
Extra: 01fc8c7b56f7f9794ffc92cc3798f6e8482d1836594aca22847115d5c00d14e14d021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e159f7be04d1b483c933948829e18d016b548a31851e102e39dbc9492f4cbca5 0.000600000000 1986683 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": 1497061, "vin": [ { "gen": { "height": 1497051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e159f7be04d1b483c933948829e18d016b548a31851e102e39dbc9492f4cbca5" } } ], "extra": [ 1, 252, 140, 123, 86, 247, 249, 121, 79, 252, 146, 204, 55, 152, 246, 232, 72, 45, 24, 54, 89, 74, 202, 34, 132, 113, 21, 213, 192, 13, 20, 225, 77, 2, 17, 0, 0, 0, 2, 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: