Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d9e0f5dd0164ce1edd2090f0ee64ea2bd48289fcb6703d96c89d2c27561a16c

Tx prefix hash: 02c51d9d27399079ca527bc9ed57ca99ee6c7c379dcd3198470a13fe6361dda8
Tx public key: b3fcb7c68bb3148be5da2ef6f6ae82b3bc8299e4767702bf7913c841ccc720a9
Timestamp: 1739519315 Timestamp [UTC]: 2025-02-14 07:48:35 Age [y:d:h:m:s]: 01:092:05:59:09
Block: 1218949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316971 RingCT/type: yes/0
Extra: 01b3fcb7c68bb3148be5da2ef6f6ae82b3bc8299e4767702bf7913c841ccc720a90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 70495271daa0e997511373db2a4eb3e15f93fc97baf83a1641496ad14d00313d 0.000600000000 1705770 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": 1218959, "vin": [ { "gen": { "height": 1218949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70495271daa0e997511373db2a4eb3e15f93fc97baf83a1641496ad14d00313d" } } ], "extra": [ 1, 179, 252, 183, 198, 139, 179, 20, 139, 229, 218, 46, 246, 246, 174, 130, 179, 188, 130, 153, 228, 118, 119, 2, 191, 121, 19, 200, 65, 204, 199, 32, 169, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: