Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3965ebba95e6aec6e4dc783085cc4de81208a56a5460447e3bf10d5d9ce47432

Tx prefix hash: 93ca42c234cccea180131d3d9b4e1f3ab9f84f6ebf516c83a8e66852c46c78ae
Tx public key: 3770add5017ae48ff5b8edc75c08f7e3bd5c1ebac46fb0b4cb4ba685db799033
Timestamp: 1685061199 Timestamp [UCT]: 2023-05-26 00:33:19 Age [y:d:h:m:s]: 01:324:17:38:21
Block: 768146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493305 RingCT/type: yes/0
Extra: 013770add5017ae48ff5b8edc75c08f7e3bd5c1ebac46fb0b4cb4ba685db79903302110000000233af99f4000000000000000000

1 output(s) for total of 1.749225836000 dcy

stealth address amount amount idx
00: 241825fdf865dedc310ff95c71d936c0e06aabf520176842864970068afae3b9 1.749225836000 1217333 of 0

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 dinasty-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": 768156, "vin": [ { "gen": { "height": 768146 } } ], "vout": [ { "amount": 1749225836, "target": { "key": "241825fdf865dedc310ff95c71d936c0e06aabf520176842864970068afae3b9" } } ], "extra": [ 1, 55, 112, 173, 213, 1, 122, 228, 143, 245, 184, 237, 199, 92, 8, 247, 227, 189, 92, 30, 186, 196, 111, 176, 180, 203, 75, 166, 133, 219, 121, 144, 51, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8