Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dccd7926cb54bfae9e196b563786d18fa7ba5386a89f8106f0cc41802b0af33

Tx prefix hash: 3efe39d4466486ed12460f3933096c86620b1c812b1148cb5b682b2c8abf21e3
Tx public key: 55f04348e6aefccfc554f11aaf87ced35898d4a871140d1706879e09379cb8f8
Timestamp: 1753707693 Timestamp [UTC]: 2025-07-28 13:01:33 Age [y:d:h:m:s]: 00:294:19:54:24
Block: 1335232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202912 RingCT/type: yes/0
Extra: 0155f04348e6aefccfc554f11aaf87ced35898d4a871140d1706879e09379cb8f8021100000005ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 389cffa8e1830ddb2a4589812468426e7c08a1c81c4bbd9cf6b1a45105a2f047 0.000600000000 1823033 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": 1335242, "vin": [ { "gen": { "height": 1335232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "389cffa8e1830ddb2a4589812468426e7c08a1c81c4bbd9cf6b1a45105a2f047" } } ], "extra": [ 1, 85, 240, 67, 72, 230, 174, 252, 207, 197, 84, 241, 26, 175, 135, 206, 211, 88, 152, 212, 168, 113, 20, 13, 23, 6, 135, 158, 9, 55, 156, 184, 248, 2, 17, 0, 0, 0, 5, 239, 34, 20, 133, 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: