Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da77770dd071b0864d74b5d0dbdfd9132ab974d7c07b7640e600a93bbe1eea63

Tx prefix hash: e8ad1a2ae39b8b1f152a68b3f63adbbbb6ac7f1b8a590c1e1377a4977c48b49c
Tx public key: bd8c722124207967ae0aab785628793719c077196a760b2384c606a2acd545f0
Timestamp: 1638786669 Timestamp [UCT]: 2021-12-06 10:31:09 Age [y:d:h:m:s]: 03:065:07:36:58
Block: 389590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 825371 RingCT/type: yes/0
Extra: 01bd8c722124207967ae0aab785628793719c077196a760b2384c606a2acd545f0021100000010f6cc1430000000000000000000

1 output(s) for total of 31.414269861000 dcy

stealth address amount amount idx
00: 412557f3b0c8bbbeaf53128a229c1bcb0c46d72d5e670fd4b6c9a2698219cce6 31.414269861000 784815 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": 389600, "vin": [ { "gen": { "height": 389590 } } ], "vout": [ { "amount": 31414269861, "target": { "key": "412557f3b0c8bbbeaf53128a229c1bcb0c46d72d5e670fd4b6c9a2698219cce6" } } ], "extra": [ 1, 189, 140, 114, 33, 36, 32, 121, 103, 174, 10, 171, 120, 86, 40, 121, 55, 25, 192, 119, 25, 106, 118, 11, 35, 132, 198, 6, 162, 172, 213, 69, 240, 2, 17, 0, 0, 0, 16, 246, 204, 20, 48, 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