Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d2bdb95e9836ef263cc35842217c5442f728157553bbc1e9505be98bd8517c6

Tx prefix hash: 10e8b8d7c064acf24b2dd3e3bc86c4e27310c54dee35cbdde3722041787b7461
Tx public key: d130ed03f2e908cbe5a97f485324e97342606ba1d9dc256e0bb31f8933f9e17f
Timestamp: 1769633746 Timestamp [UTC]: 2026-01-28 20:55:46 Age [y:d:h:m:s]: 00:296:18:58:41
Block: 1465722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217772 RingCT/type: yes/0
Extra: 01d130ed03f2e908cbe5a97f485324e97342606ba1d9dc256e0bb31f8933f9e17f02110000000f215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd676ed86ab89d9b80a42ff26b8f32c737ea2edd83a810f74f36d41bce56b92c 0.000600000000 1954952 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": 1465732, "vin": [ { "gen": { "height": 1465722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd676ed86ab89d9b80a42ff26b8f32c737ea2edd83a810f74f36d41bce56b92c" } } ], "extra": [ 1, 209, 48, 237, 3, 242, 233, 8, 203, 229, 169, 127, 72, 83, 36, 233, 115, 66, 96, 107, 161, 217, 220, 37, 110, 11, 179, 31, 137, 51, 249, 225, 127, 2, 17, 0, 0, 0, 15, 33, 91, 191, 137, 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: