Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5401b02db18ec45eea73eee5c9a2595ee301e4ebe17ed90b1a51591f240e55e

Tx prefix hash: a278b9f39b0654c5f30c7abc31ce8d38e397701536a6886d5b31062b8c3448d7
Tx public key: 0d404fc5e0c8db0eaeafda2f7bf74acc960cea1b05b1d4c0d90571b6dbd2f02f
Timestamp: 1772664378 Timestamp [UTC]: 2026-03-04 22:46:18 Age [y:d:h:m:s]: 00:258:14:54:08
Block: 1490801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190367 RingCT/type: yes/0
Extra: 010d404fc5e0c8db0eaeafda2f7bf74acc960cea1b05b1d4c0d90571b6dbd2f02f021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b2667a9e35a585ab4c55a2b49ccfd6680ce2e805e679ce0a41c488f040824fc7 0.000600000000 1980311 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": 1490811, "vin": [ { "gen": { "height": 1490801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2667a9e35a585ab4c55a2b49ccfd6680ce2e805e679ce0a41c488f040824fc7" } } ], "extra": [ 1, 13, 64, 79, 197, 224, 200, 219, 14, 174, 175, 218, 47, 123, 247, 74, 204, 150, 12, 234, 27, 5, 177, 212, 192, 217, 5, 113, 182, 219, 210, 240, 47, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: