Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6d017627305e1e2d83503596579878c77a2d04a171c9ef0a4365a19dc6e35c

Tx prefix hash: af76042c70df69889efc8c4510b55af4397fcda7de05ddef4264f7c54695d5d8
Tx public key: ba0dedca6674698196d2e53d10c7c4975b7e175d6e1ae67acc995dc944d7f23a
Timestamp: 1675605624 Timestamp [UCT]: 2023-02-05 14:00:24 Age [y:d:h:m:s]: 02:083:09:08:00
Block: 690391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581228 RingCT/type: yes/0
Extra: 01ba0dedca6674698196d2e53d10c7c4975b7e175d6e1ae67acc995dc944d7f23a0211000000035029cbac000000000000000000

1 output(s) for total of 3.165541048000 dcy

stealth address amount amount idx
00: a7569d33a8fd387c64c878308c81615db5f7c927348878c5be8143a7f9d6f2a3 3.165541048000 1133117 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": 690401, "vin": [ { "gen": { "height": 690391 } } ], "vout": [ { "amount": 3165541048, "target": { "key": "a7569d33a8fd387c64c878308c81615db5f7c927348878c5be8143a7f9d6f2a3" } } ], "extra": [ 1, 186, 13, 237, 202, 102, 116, 105, 129, 150, 210, 229, 61, 16, 199, 196, 151, 91, 126, 23, 93, 110, 26, 230, 122, 204, 153, 93, 201, 68, 215, 242, 58, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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