Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cac2f5a5a1afc84635fceb33f2c6b0516fad354125318f9f77d58abaef08bd7

Tx prefix hash: e10e08eade1cb6594fe2ce4b446a0cd40c7ba9791a58704af595d451331b044c
Tx public key: 3a77dc4b6084f0e1f87000c24c1bcf447a1f4f4d6767391ece32f9abef7d3ef0
Timestamp: 1750830079 Timestamp [UTC]: 2025-06-25 05:41:19 Age [y:d:h:m:s]: 01:149:11:11:27
Block: 1312331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371163 RingCT/type: yes/0
Extra: 013a77dc4b6084f0e1f87000c24c1bcf447a1f4f4d6767391ece32f9abef7d3ef0021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d203f51bf4132babce1853aba0650e73cebb9cf2fcd6a5b1ed5b79d62c8ff2c 0.000600000000 1799964 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": 1312341, "vin": [ { "gen": { "height": 1312331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d203f51bf4132babce1853aba0650e73cebb9cf2fcd6a5b1ed5b79d62c8ff2c" } } ], "extra": [ 1, 58, 119, 220, 75, 96, 132, 240, 225, 248, 112, 0, 194, 76, 27, 207, 68, 122, 31, 79, 77, 103, 103, 57, 30, 206, 50, 249, 171, 239, 125, 62, 240, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: