Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b759b94681f75c985f022768969b33bc8e08128fe6bdc64e4bcc65451c84c2d1

Tx prefix hash: 99bf692aebc0e7f33b7ba0fc0a38b6700da950704a3d1a6d0acb4fa3df2708ec
Tx public key: 0b0c338696b522ed1fbf1e6d1ed40479c32a318dc5e4192a3f968eaed724d457
Timestamp: 1745104291 Timestamp [UTC]: 2025-04-19 23:11:31 Age [y:d:h:m:s]: 01:019:23:01:41
Block: 1265176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265471 RingCT/type: yes/0
Extra: 010b0c338696b522ed1fbf1e6d1ed40479c32a318dc5e4192a3f968eaed724d4570211000000096c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bab256233b50094d0d5114c9df0f23d85646032f8afbb834dd8bd72c654fec19 0.000600000000 1752379 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": 1265186, "vin": [ { "gen": { "height": 1265176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bab256233b50094d0d5114c9df0f23d85646032f8afbb834dd8bd72c654fec19" } } ], "extra": [ 1, 11, 12, 51, 134, 150, 181, 34, 237, 31, 191, 30, 109, 30, 212, 4, 121, 195, 42, 49, 141, 197, 228, 25, 42, 63, 150, 142, 174, 215, 36, 212, 87, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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: