Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b8b3e9755be69b5fa8e4c8916daf9d066f160ad3a9302b2a67986372bfbfce

Tx prefix hash: eccf8c6137d636c8fea1a3b31ab87768259a473dd40f3a5c33c823bd22dfc286
Tx public key: f19640e0bd74bad6f121e607a7c934e5df0efa70890dfac13f8178d411eb8285
Timestamp: 1698911390 Timestamp [UCT]: 2023-11-02 07:49:50 Age [y:d:h:m:s]: 01:141:04:12:50
Block: 882928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361888 RingCT/type: yes/0
Extra: 01f19640e0bd74bad6f121e607a7c934e5df0efa70890dfac13f8178d411eb828502110000000333af99f4000000000000000000

1 output(s) for total of 0.728606470000 dcy

stealth address amount amount idx
00: 32461b5bf1aee4f45fc62e2b59f53540aeb25983e57b31e0380cd4f904c19882 0.728606470000 1338610 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": 882938, "vin": [ { "gen": { "height": 882928 } } ], "vout": [ { "amount": 728606470, "target": { "key": "32461b5bf1aee4f45fc62e2b59f53540aeb25983e57b31e0380cd4f904c19882" } } ], "extra": [ 1, 241, 150, 64, 224, 189, 116, 186, 214, 241, 33, 230, 7, 167, 201, 52, 229, 223, 14, 250, 112, 137, 13, 250, 193, 63, 129, 120, 212, 17, 235, 130, 133, 2, 17, 0, 0, 0, 3, 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