Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfd3fab4c860a289e9cf590f86b4e3c24ef569c52d7748ed0e62863019a097af

Tx prefix hash: d9218e738c804c0a9deb74259d3a9df6b9ce22c9a69f227457212785ef0283d2
Tx public key: 527fd6e84f14565dbb235e96b1ceace9fccd2ed9c919848138b0e62f6309ee11
Timestamp: 1774330438 Timestamp [UTC]: 2026-03-24 05:33:58 Age [y:d:h:m:s]: 00:237:14:55:38
Block: 1504574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175311 RingCT/type: yes/0
Extra: 01527fd6e84f14565dbb235e96b1ceace9fccd2ed9c919848138b0e62f6309ee11021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3c8f1f5d0dfd8679442fc939f88b8c45a8d1678a3fc1de46f0decf17ce26ba6 0.000600000000 1994298 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": 1504584, "vin": [ { "gen": { "height": 1504574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3c8f1f5d0dfd8679442fc939f88b8c45a8d1678a3fc1de46f0decf17ce26ba6" } } ], "extra": [ 1, 82, 127, 214, 232, 79, 20, 86, 93, 187, 35, 94, 150, 177, 206, 172, 233, 252, 205, 46, 217, 201, 25, 132, 129, 56, 176, 230, 47, 99, 9, 238, 17, 2, 17, 0, 0, 0, 4, 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: