Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ca9c7853d56aca75359adba6661cf9a64e8ea70d52395e388548585e241f9f

Tx prefix hash: e9da3c4b78e6890d4fb8177c5606dbc73ce4c2334842307fd55e94a2a66c63fe
Tx public key: b86521c186760964c43a156fc5f26211e5bbea2813cd9a8b1324dc33a7ecb7b7
Timestamp: 1701047309 Timestamp [UCT]: 2023-11-27 01:08:29 Age [y:d:h:m:s]: 01:054:07:23:32
Block: 900422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300171 RingCT/type: yes/0
Extra: 01b86521c186760964c43a156fc5f26211e5bbea2813cd9a8b1324dc33a7ecb7b7021100000002e08532b6000000000000000000

1 output(s) for total of 0.637570352000 dcy

stealth address amount amount idx
00: 5e1027e4bb07e36145db377b36433cd94e081a5624cbf1bb947f90ba511c0c32 0.637570352000 1356923 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": 900432, "vin": [ { "gen": { "height": 900422 } } ], "vout": [ { "amount": 637570352, "target": { "key": "5e1027e4bb07e36145db377b36433cd94e081a5624cbf1bb947f90ba511c0c32" } } ], "extra": [ 1, 184, 101, 33, 193, 134, 118, 9, 100, 196, 58, 21, 111, 197, 242, 98, 17, 229, 187, 234, 40, 19, 205, 154, 139, 19, 36, 220, 51, 167, 236, 183, 183, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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