Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d1bbb14087608995b46a361daa589cb334310d86a954d5ddd495ea4bae66a5

Tx prefix hash: 81e6c143036b5d7ec6e7101de4100ae1f3598484222a6166f401668616fff0f5
Tx public key: cf2ace2a4c13b3b335f7a1ba2ad957e54995ffcb235091b0da45c96542e1e356
Timestamp: 1582098621 Timestamp [UCT]: 2020-02-19 07:50:21 Age [y:d:h:m:s]: 05:259:21:55:20
Block: 67935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336646 RingCT/type: yes/0
Extra: 01cf2ace2a4c13b3b335f7a1ba2ad957e54995ffcb235091b0da45c96542e1e35602110000000cd81c26c0000000000000000000

1 output(s) for total of 365.513944862000 dcy

stealth address amount amount idx
00: 63aace7fc08a12f8b8ad18506d7eb3d8ccfe13b2986836e6e2414ca79f70317d 365.513944862000 125157 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": 67945, "vin": [ { "gen": { "height": 67935 } } ], "vout": [ { "amount": 365513944862, "target": { "key": "63aace7fc08a12f8b8ad18506d7eb3d8ccfe13b2986836e6e2414ca79f70317d" } } ], "extra": [ 1, 207, 42, 206, 42, 76, 19, 179, 179, 53, 247, 161, 186, 42, 217, 87, 229, 73, 149, 255, 203, 35, 80, 145, 176, 218, 69, 201, 101, 66, 225, 227, 86, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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