Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c30f41d5810944bc32813deab473ab0ba220ed01fed9c9607468b49aecb5f7e

Tx prefix hash: 0b65eccb30d326257f4dfa8cd4265f5c3c300f9d885471c3793916860f39f61a
Tx public key: f506b5a706d1be8e638fbf9e258fcde5540642f12b7fd3fc3cd61b2faa2ccb7b
Timestamp: 1712528871 Timestamp [UCT]: 2024-04-07 22:27:51 Age [y:d:h:m:s]: 00:349:07:35:10
Block: 995581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249777 RingCT/type: yes/0
Extra: 01f506b5a706d1be8e638fbf9e258fcde5540642f12b7fd3fc3cd61b2faa2ccb7b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2adf611482e8967298c234ba87c05bf560f3698aaa37bb7a8c583d94621e3dcb 0.600000000000 1455991 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": 995591, "vin": [ { "gen": { "height": 995581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2adf611482e8967298c234ba87c05bf560f3698aaa37bb7a8c583d94621e3dcb" } } ], "extra": [ 1, 245, 6, 181, 167, 6, 209, 190, 142, 99, 143, 191, 158, 37, 143, 205, 229, 84, 6, 66, 241, 43, 127, 211, 252, 60, 214, 27, 47, 170, 44, 203, 123, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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