Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8185cfc6da12e5b06e5ba40f76db96493e81ae140601303f16994952d1a92596

Tx prefix hash: 045206e581a5464bbd08a1f2f9b2274a0e5328341e6d2f9e4cd5891c97fc6c4c
Tx public key: 0b4f161b030d1c78475840b97dc05e87cc0e8e0223701a37335cb05807763c2b
Timestamp: 1743725197 Timestamp [UTC]: 2025-04-04 00:06:37 Age [y:d:h:m:s]: 00:317:16:44:49
Block: 1253760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224695 RingCT/type: yes/0
Extra: 010b4f161b030d1c78475840b97dc05e87cc0e8e0223701a37335cb05807763c2b021100000004a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e95e1bc7913c3f39adb8982ecde8e5bb74ad351315141c5b8ed3591de5e9f81a 0.000600000000 1740841 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": 1253770, "vin": [ { "gen": { "height": 1253760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95e1bc7913c3f39adb8982ecde8e5bb74ad351315141c5b8ed3591de5e9f81a" } } ], "extra": [ 1, 11, 79, 22, 27, 3, 13, 28, 120, 71, 88, 64, 185, 125, 192, 94, 135, 204, 14, 142, 2, 35, 112, 26, 55, 51, 92, 176, 88, 7, 118, 60, 43, 2, 17, 0, 0, 0, 4, 162, 237, 1, 107, 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) | dinastycoin version: tesla-369