Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b97173c716e80c11bd4a95bab3bfede8ee6c8f7c114ef4fa4eaa0f450afec433

Tx prefix hash: 3eb8c1454458dca35cd5d68ade78c3b680bd99b37c85d26c4c7705cb4edb478d
Tx public key: 28c40952bff9d4027cf7c6e5c9f06f7b01f532d602ef0813761382bec6ad1a34
Timestamp: 1770203928 Timestamp [UTC]: 2026-02-04 11:18:48 Age [y:d:h:m:s]: 00:286:01:38:41
Block: 1470463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209925 RingCT/type: yes/0
Extra: 0128c40952bff9d4027cf7c6e5c9f06f7b01f532d602ef0813761382bec6ad1a34021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1e7b459183e95ca0d300f9d5e220a44aa8e91782dade5bfdc3827eef6d6de3cb 0.000600000000 1959731 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": 1470473, "vin": [ { "gen": { "height": 1470463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e7b459183e95ca0d300f9d5e220a44aa8e91782dade5bfdc3827eef6d6de3cb" } } ], "extra": [ 1, 40, 196, 9, 82, 191, 249, 212, 2, 124, 247, 198, 229, 201, 240, 111, 123, 1, 245, 50, 214, 2, 239, 8, 19, 118, 19, 130, 190, 198, 173, 26, 52, 2, 17, 0, 0, 0, 6, 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: