Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44325f3c69f30d91200c75370bb6c32c9200a7b5b0bbf8345d52bfe652e9d176

Tx prefix hash: 77099dac6fd33e1cb91b2d2d16045f5fa6b0a94d632bbafc1b3a797a0c1fb88a
Tx public key: 76eb7935a141a5bc2cf8639667eedd468f808cd398d02d64411657c61b0b0f48
Timestamp: 1706305435 Timestamp [UCT]: 2024-01-26 21:43:55 Age [y:d:h:m:s]: 01:071:17:32:03
Block: 943988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312362 RingCT/type: yes/0
Extra: 0176eb7935a141a5bc2cf8639667eedd468f808cd398d02d64411657c61b0b0f480211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da7c3e4788c6c3d162432aea0ba6c61f27cd6dc9ed8bb55aecfb448d6c60647c 0.600000000000 1402214 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 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": 943998, "vin": [ { "gen": { "height": 943988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da7c3e4788c6c3d162432aea0ba6c61f27cd6dc9ed8bb55aecfb448d6c60647c" } } ], "extra": [ 1, 118, 235, 121, 53, 161, 65, 165, 188, 44, 248, 99, 150, 103, 238, 221, 70, 143, 128, 140, 211, 152, 208, 45, 100, 65, 22, 87, 198, 27, 11, 15, 72, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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