Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e974d506a6c7f0e6bd29914be0e886573a2c02dbfcac2ca4bf4bdfb5b9d5cc

Tx prefix hash: 23ff9f668d1b90dc62285d08e957899f031ae7a0ae88fadc9112ef2460c5114d
Tx public key: 0db916907a7189085394d007ffa45a6e5b1d0750e9cc0477055423ae0c094029
Timestamp: 1770984703 Timestamp [UTC]: 2026-02-13 12:11:43 Age [y:d:h:m:s]: 00:103:22:54:35
Block: 1476915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 68358 RingCT/type: yes/0
Extra: 010db916907a7189085394d007ffa45a6e5b1d0750e9cc0477055423ae0c09402902085c5d6f51f4d5e998

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6bdfd37fe7b51c5e125a7e183ad10a30747a98a50cb13b769e3e2ae3dc87d4e9 0.000600000000 1966227 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": 1476925, "vin": [ { "gen": { "height": 1476915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bdfd37fe7b51c5e125a7e183ad10a30747a98a50cb13b769e3e2ae3dc87d4e9" } } ], "extra": [ 1, 13, 185, 22, 144, 122, 113, 137, 8, 83, 148, 208, 7, 255, 164, 90, 110, 91, 29, 7, 80, 233, 204, 4, 119, 5, 84, 35, 174, 12, 9, 64, 41, 2, 8, 92, 93, 111, 81, 244, 213, 233, 152 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: