Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086679135c2682a9aa72f682bb4638ce9654a19e3d609094f221410e50780d91

Tx prefix hash: 0dcd0f0c003cb3363f914304d2a3ce33fccf9de76ae5f169770ffed51b92f50c
Tx public key: 2e5b995edc017cfb1c802c99b7149619f6f64f3887493876a1dd79bc3f44d1fb
Timestamp: 1703618192 Timestamp [UCT]: 2023-12-26 19:16:32 Age [y:d:h:m:s]: 01:110:03:18:13
Block: 921742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339825 RingCT/type: yes/0
Extra: 012e5b995edc017cfb1c802c99b7149619f6f64f3887493876a1dd79bc3f44d1fb02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f63d42ef6fd385488c5ea868316d4bdcf5ae210942ff81d4b5f1dce8cf2cad30 0.600000000000 1379436 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": 921752, "vin": [ { "gen": { "height": 921742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f63d42ef6fd385488c5ea868316d4bdcf5ae210942ff81d4b5f1dce8cf2cad30" } } ], "extra": [ 1, 46, 91, 153, 94, 220, 1, 124, 251, 28, 128, 44, 153, 183, 20, 150, 25, 246, 246, 79, 56, 135, 73, 56, 118, 161, 221, 121, 188, 63, 68, 209, 251, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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